docs: add "Bring your data" step to homepage journey#29
Merged
Conversation
The homepage's "How It Works" jumped from "Create your AI workspace" straight to "Define a use case", with "Select datasets" framed as a sub-action of use-case definition. That inverted the actual journey (ingest first, then define a use case from your prepared datasets) and contradicted /create-use-case, which gets it right. Adds an explicit "Bring your data" step between workspace creation and use-case definition, and rewords Step 2 + the Next Steps card so "Select datasets" no longer reads as a UI action performed during use-case creation. Closes #28 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
👋 Heads-up — Code review queue is at 14 / 8 Above the WIP limit. The team convention is to review existing PRs before opening new work. Open PRs currently in Code review (oldest first):
Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.) |
The hero CardGroup at the top of the homepage said "Define datasets, set metrics, invite contributors" — same inversion as the "How It Works" steps and the "Next Steps" card, framing datasets as something configured during use-case creation. The previous commit fixed the two visible spots but missed this one. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
aptracebloc
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The homepage previously inverted the actual journey: it jumped from "Create your AI workspace" straight to "Define a use case", with datasets selected as a sub-action of that step. That contradicted
/create-use-case(which correctly lists ingestion as the first workflow step) and sent newcomers into the platform looking for a dataset selector with no datasets to select.Cross-references the same bug class in tracebloc/data-ingestors#66 (Readme prereq listed "active use case" as required before ingest).
Closes #28
Diff
Test plan
<Steps>block correctly (was 5)./create-use-caseordering.🤖 Generated with Claude Code
Note
Low Risk
Low risk documentation-only update that reorders and rewords homepage guidance; the main risk is minor messaging/UX confusion if the new step copy is inaccurate.
Overview
Updates the
overview/tracebloc.mdxhomepage journey to explicitly include a “Bring your data” step between workspace setup and use-case definition, clarifying that datasets are validated/staged on the user’s cluster and only metadata syncs.Rewords related copy in the hero and “Next Steps” cards and the “Define a use case” step to emphasize picking from prepared datasets rather than selecting datasets during use-case creation.
Reviewed by Cursor Bugbot for commit a5bd224. Bugbot is set up for automated code reviews on this repo. Configure here.